Don't check positions in findTreesMatching
#5222
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We used to check the positions in `findTreesMatching` and exclude trees where the position is not source-derived. It turns out that this is wrong, because this will exclude all trees that have been unpickled. The correct test, checking whether the position has a zero extent, is already done in `namedTrees`.
smarter
approved these changes
Oct 9, 2018
|
I opened #5223 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We used to check the positions in
findTreesMatchingand exclude treeswhere the position is not source-derived. It turns out that this is
wrong, because this will exclude all trees that have been unpickled.
The correct test, checking whether the position has a zero extent, is
already done in
namedTrees.